Accumulator for prefetch abort

ABSTRACT

The present invention relates to systems, apparatus, and methods of determining whether to abort a prefetch operation. Embodiments include accumulator functionality for accumulating object data prior to making an abort determination. Certain embodiments compress the accumulated data to more accurately reflect the cost of pushing the data to the client as part of the prefetch operation. Accumulation and/or compression of the data may provide sufficient data relating to the size of the object to make a useful prefetch abort determination, even where the size of the object cannot be otherwise determined (e.g., from the object data header). Other embodiments store accumulated data (e.g., in compressed or uncompressed form) for use in further optimizing prefetch operations. For example, if an accumulated prefetch is aborted before the object is forwarded to the client, and the client later requests the object, the object may be pushed to the client from server-side storage, rather than retrieving (e.g., and compressing) the object from the content server redundantly.

CROSS-REFERENCES

The present application is a continuation-in-part of co-pending, commonly assigned U.S. patent application Ser. No. 12/172,913, filed on Jul. 14, 2008, entitled “METHODS AND SYSTEMS FOR PERFORMING A PREFETCH ABORT OPERATION,” Attorney Docket No. 026841-000110US, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/949,492, filed Jul. 12, 2007, entitled “METHODS AND SYSTEMS FOR PERFORMING A PREFETCH ABORT OPERATION,” Attorney Docket No. 026841-000100US, both of which are hereby incorporated by reference herein in their entirety for all purposes. The present application also claims the benefit of U.S. Provisional Patent Application Ser. No. 61/253,947, filed Oct. 22, 2009, entitled “OPTIMIZED PREFETCH ABORT,” Attorney Docket No. 017018-021000US, which is hereby incorporated by reference herein in its entirety for all purposes.

FIELD OF THE INVENTION

The present invention relates, in general, to network acceleration and, more particularly, to performing prefetch abort operations.

BACKGROUND

Presently, prefetching blindly downloads content which may or may not be utilized by a client system in the future. Such an operation is performed without any consideration for the probability that the object may actually be used, nor does prefetching take into consideration the size of the object, the bandwidth of the link between the client and the content server, etc. As a result, a considerable amount of bandwidth, server capacity, and storage space is wasted on prefetched content which is never actually used. Hence, improvements in the art are needed.

BRIEF SUMMARY

Among other things, systems and methods are described for determining whether to abort a prefetch operation. Some prefetch abort determinations are made according to the size of the object being prefetched. However, in some cases, it is difficult or impossible to determine the size of the object prior to downloading the object from a content server. As such, embodiments include accumulator functionality for accumulating object data prior to making an abort determination. Certain embodiments also compress the accumulated data to more accurately reflect the cost of pushing the data to the client as part of the prefetch operation. Accumulation and/or compression of the data may provide sufficient data relating to the size of the object to make a useful abort determination, even where the size of the object cannot be otherwise determined (e.g., from the object data header). Other embodiments store accumulated data (e.g., in compressed or uncompressed form) for use in further optimizing prefetch operations. For example, if an accumulated prefetch is aborted before the object is forwarded to the client, and the client later requests the object, the object may be pushed to the client from server-side storage, rather than retrieving (e.g., and compressing) the object from the content server redundantly. Still other embodiments exploit the accumulated data to implement additional (e.g., byte-level) data processing functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components. In some instances, a sub-label is associated with a reference numeral to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components.

FIG. 1 is a block diagram illustrating a system for performing prefetch abort operations, according to embodiments of the present invention.

FIG. 2 is a flow diagram illustrating a method for performing prefetch abort operations, according to one embodiment of the present invention.

FIG. 3 is a block diagram illustrating a system for accelerating network communications, according to one embodiment of the present invention.

FIG. 4 is a generalized schematic diagram illustrating a computer system, in accordance with various embodiments of the invention.

FIG. 5 is a block diagram illustrating a networked system of computers, which can be used in accordance with various embodiments of the invention.

FIG. 6 shows a flow diagram of an illustrative method 600 for prefetching using an accumulator, according to various embodiments.

FIG. 7 shows relevant portions of an illustrative communications system 700, including an accumulator for a prefetch abort system, according to various embodiments.

FIG. 8 shows an illustrative method 800 for exploiting accumulated data to further optimize prefetch abort operations, according to various embodiments.

DETAILED DESCRIPTION OF THE INVENTION

While various aspects of embodiments of the invention have been summarized above, the following detailed description illustrates exemplary embodiments in further detail to enable one of skill in the art to practice the invention. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form. Several embodiments of the invention are described below and, while various features are ascribed to different embodiments, it should be appreciated that the features described with respect to one embodiment may be incorporated with another embodiment as well. By the same token, however, no single feature or features of any described embodiment should be considered essential to the invention, as other embodiments of the invention may omit such features.

Aspects of the present invention relate to performing prefetch abort operations. A prefetch abort operation allows for a proxy server to abort the prefetching of various objects. Whether or not to abort a prefetch is determined by performing a cost-benefit analysis on the object to be prefetched. Based on various factors, if the cost of prefetching an object outweighs the benefit, then the prefetch operation is aborted, thus allowing for a more efficient use of server resources as well as better network acceleration.

Turning now to FIG. 1, a system 100 for optimizing transfer of content from the Internet to a web browser is illustrated. In one embodiment, the system may include a user system 102, a proxy client 112, and a proxy server 132. The user system 102 may include a client graphical user interface (GUI) 110. Client GUI 110 may allow a user to configure performance aspects of the system 100. For example, the user may adjust the compression parameters and/or algorithms, content filters (e.g., blocks elicit websites), and enable or disable various features used by the system 100. In one embodiment, some of the features may include network diagnostics, error reporting, as well as controlling, for example, prefetch response abort 142. Such control may be adding and/or removing pages (i.e. URLs) to or from whitelist 148 and/or blacklist 149.

In one embodiment, the user selects a universal recourse locator (URL) address which directs web browser 106 (e.g., Internet Explorer®, Firefox®, Netscape Navigator®, etc.) to a website (e.g., cnn.com, google.com, yahoo.com, etc.). In a further embodiment, web browser 106 may check browser cache 104 to determine whether the website associated with the selected URL is located within browser cache 104. If the website is located within browser cache 104, the amount of time the website has been in the cache is checked to determine if the cached website is “fresh” (i.e., new) enough to use. For example, the amount of time that a website may be considered fresh may be 5 minutes; however, other time limits may be used. Consequently, if the website has been cached and the website is considered fresh, then web browser 106 renders the cached page. However, if the website has either not been cached or the cached webpage is not fresh, web browser 106 sends a request to the Internet for the website.

In one embodiment, redirector 108 intercepts the request sent from web browser 106. Redirector 108 instead sends the request through a local bus 105 to proxy client 112. In some embodiments, proxy client 112 may be implemented as a software application running on user system 102. In an alternative embodiment, proxy client 112 may be implemented on a separate computer system and is connected to user system 102 via a high speed/low latency link (e.g., a branch office LAN subnet, etc.). In one embodiment, proxy client 112 includes a request parser 116. Request parser 116 may check cache optimizer 114 to determine if a cached copy of the requested website may still be able to be used. Cache optimizer 114 is in communication with browser cache 104 in order to have access to cached websites. Cache optimizer 114 is able to access browser cache 104 without creating a redundant copy of the cached websites, thus requiring less storage space.

According to one embodiment, cache optimizer 114 implements more effective algorithms to determine whether a cached website is fresh. In one embodiment, cache optimizer 114 may implement the cache expiration algorithms from HTTP v1.1 (i.e., RFC 2616), which may not be natively supported in web browser 106. For example, browser cache 104 may inappropriately consider a cached website as too old to use; however, cache optimizer 114 may still be able to use the cached website. More efficient use of cached websites can improve browsing efficiency by reducing the number of Internet accesses.

In one embodiment, if the requested website is not able to be accessed from the cached websites, request parser 116 checks prefetch manager 120 to determine if the requested website has been prefetched. Prefetching a website is when content from the website is accessed, downloaded, and stored before a request to the website is made by web browser 106. Prefetching can potentially save round-trips of data access from user system 102 to the Internet.

In a further embodiment, if the requested website has not been prefetched, then request parser 116 forwards the request to a request encoder 118. Request encoder 118 encodes the request into a compressed version of the request using one of many possible data compression algorithms. For example, these algorithms may employ a coding dictionary 122 which stores strings so that data from previous web objects can be used to compress data from new pages. Accordingly, where the request for the website is 550 bytes in total, the encoded request may be as small as 50 bytes. This level of compression can save bandwidth on a connection, such as high latency link 130. In one embodiment, high latency link 130 may be a wireless link, a cellular link, a satellite link, a dial-up link, etc.

In one embodiment, after request encoder 118 generates an encoded version of the request, the encoded request is forwarded to a protocol 128. In one embodiment, protocol 128 is Intelligent Compression Technology's® (ICT) transport protocol (ITP). Nonetheless, other protocols may be used, such as the standard transmission control protocol (TCP). In one embodiment, ITP maintains a persistent connection with proxy server 132. The persistent connection between proxy client 112 and proxy server 132 enables system 100 to eliminate the inefficiencies and overhead costs associated with creating a new connection for each request.

In one embodiment, the encoded request is forwarded from protocol 128 to request decoder 136. Request decoder 136 uses a decoder which is appropriate for the encoding performed by request encoder 118. In one embodiment, this process utilizes a coding dictionary 138 in order to translate the encoded request back into a standard format which can be accessed by the destination website. Furthermore, if the HTTP request includes a cookie (or other special instructions), such as a “referred by” or type of encoding accepted, information about the cookie or instructions may be stored in a cookie model 152. Request decoder 136 then transmits the decoded request to the destination website over a low latency link 156. Low latency link 156 may be, for example, a cable modem connection, a digital subscriber line (DSL) connection, a T1 connection, a fiber optic connection, etc.

In response to the request, a response parser 144 receives a response from the requested website. In one embodiment, this response may include an attachment, such as an image and/or text file. Some types of attachments, such as HTML, XML, CSS, or Java Scripts, may include references to other “in-line” objects that may be needed to render a requested web page. In one embodiment, when response parser 144 detects an attachment type that may contain such references to “in-line” objects, response parser 144 may forward the objects to a prefetch scanner 146.

In one embodiment, prefetch scanner 146 scans the attached file and identifies URLs of in-line objects that may be candidates for prefetching. For example, candidates may be identified by HTML syntax, such as the token “img src=”. In addition, objects that may be needed for the web page may also be specified in java scripts that appear within the HTML or CSS page or within a separate java script file. Methods for identifying candidates within Java scripts may be found in a co-pending U.S. patent application entitled, “METHODS AND SYSTEMS FOR JAVA SCRIPT PARSING”, Attorney Docket No. 026841-00210US, filed concurrently herewith which is incorporated by reference for any and all purposes. In one embodiment, the identified candidates are added to a candidate list.

In one embodiment, for the candidate URLs, prefetch scanner 146 may notify prefetch response abort 142 of the context in which the object was identified, such as the type of object in which it was found and/or the syntax in which the URL occurred. This information may be used by prefetch response abort 142 to determine the probability that the URL will actually be requested by web browser 106.

According to a further embodiment, the candidate list is forwarded to whitelist 148 and blacklist 149. Whitelist 148 and blacklist 149 may be used to track which URLs should be allowed to be prefetched. Based on the host (i.e., the server that is supplying the URL), the file type (e.g., application service provider (ASP) files should not be prefetched), etc. Accordingly, whitelist 148 and blacklist 149 control prefetching behavior by indicating which URLs on the candidate list should or should not be prefetched. In many instances with certain webpages/file types, prefetching may not work. In addition to ASP files, webpages which include fields or cookies may have problems with prefetching.

In one embodiment, once the candidate list has been passed through whitelist 148 and blacklist 149, a modified candidate list is generated and then the list is forwarded to a client cache model 150. The client cache model 150 attempts to model which items from the list will be included in browser cache 104. As such, those items are removed from the modified candidate list. Subsequently, the updated modified candidate list is forwarded to a request synthesizer 154 which creates an HTTP request in order to prefetch each item in the updated modified candidate list. The HTTP request header may include cookies and/or other instructions appropriate to the website and/or to web browser 106's preferences using information obtained from cookie model 152. The prefetch HTTP requests may then be transmitted through low latency link 156 to the corresponding website.

In one embodiment, response parser 144 receives a prefetch response from the website and accesses a prefetch response abort 142. Prefetch response abort 142 is configured to determine whether the prefetched item is worth sending to user system 102. Prefetch response abort 142 bases its decision whether to abort a prefetch on a variety of factors, which are discussed below in more detail.

If the prefetch is not aborted, response parser 144 forwards the response to response encoder 140. Response encoder 140 accesses coding dictionary 138 in order to encode the prefetched response. Response encoder 140 then forwards the encoded response through protocol 128 over high latency link 130 and then to response decoder 126. Response decoder 126 decodes the response and forwards the response to response manager 124. In one embodiment, if the response is a prefetched response, then response manager 124 creates a prefetch socket to receive the prefetched item as it is downloaded.

Response manager 124 transmits the response over local bus 105 to redirector 108. Redirector 108 then forwards the response to web browser 106 which renders the content of the response.

Turning now to FIG. 2, which illustrates method 200, one embodiment of the operations performed by prefetch response abort 142 (FIG. 1) is shown. As discussed above, prefetch response abort 142 (FIG. 1) receives a prefetched object from the Internet through low latency link 156 (FIG. 1) (process block 205). Even though the object has initially been prefetched, it does not necessarily mean that it is efficient to forward the object to the client (e.g., proxy client 112 (FIG. 1)). Due to bandwidth and other constraints of the link, objects sent over high latency link 130 (FIG. 1) between proxy server 132 (FIG. 1) and proxy client 112 (FIG. 1) should be carefully selected. Accordingly, a variety of factors should be considered before forwarding a prefetched object to the client.

At process block 210, the size of the received object is checked. In one embodiment, the size of the object may be significant in determining whether to forward the object to the client. For example, one benefit of forwarding the prefetched object to the client may be the elimination of a round trip. In other words, if a prefetched item is eventually used by user system 102 (FIG. 1), the request out to the Internet and the response back from the requested website (i.e., one round trip) can be eliminated. Hence, in some instances, the smaller the prefetched object is, the more beneficial the prefetch is for optimization purposes.

Furthermore, one potential negative effect of forwarding a prefetched object is that the prefetched object unnecessarily uses the link's bandwidth. As such, if a prefetched object is forwarded to the client but never used by the client, the bandwidth used to forward the object may be wasted. Accordingly, larger prefetched objects may decrease optimization because the gained round trip may not outweigh the bandwidth consumption. In one embodiment, a point system may be assigned to the prefetched object where, for example, a 10 kilobyte object is given a higher point value than a 10 megabyte object. Consequently, if the point value associated with the object reaches or exceeds a threshold, then the object is forwarded to the client.

Another factor in determining whether an object should be forwarded to the client is the probability of use of the object (process block 215). As a user browses the Internet, not all URLs that are prefetched will actually be requested by web browser 106. The user may, for example, “click-off” a web page before objects within the page are requested. Whether some objects may be requested may depend on browser settings and/or on external events, such as mouse position. Furthermore, objects referenced on a CSS (e.g., style sheet for the entire website) may not be used on each individual web page. In addition, if URLs are identified within Java scripts, the scripts themselves, based on a variety of factors, may determine whether to request an object.

In one embodiment, the probability that an object will actually be requested by web browser 106 may be estimated as a function of the context in which the reference was identified. For example, this context may depend on the type of the object (e.g., HTML, CSS, JS, etc.), the surrounding syntax (e.g., “img src=”, java script, etc.), and the level of recursion (e.g., was the reference on the main HTML or on an object that was itself prefetched). In one embodiment, if the object was referenced in a Java script, the probability of use may depend on information collected while parsing the script. The probability that an object in a specific context will be requested can be estimated in several ways. For example, a general model can be built sampling many different clients in many sessions going to many websites. Subsequently, a more specific model can be developed for a specific website and/or for a particular user. In one embodiment, this may be accomplished by recording the frequency of page use in a specific context for a specific web page by a specific user.

Collectively, based on the above-mentioned probability factors, the object may be assigned a point value associated with its probability of use. In an alternative embodiment, the probability of use may be assigned a percentage value.

At process block 220, the bandwidth of high latency link 130 (FIG. 1) may be determined (i.e., the speed of the link between proxy server 132 (FIG. 1) and proxy client 112 (FIG. 1)). The bandwidth of this link can be a factor in determining whether to forward the prefetched object. For example, with a higher link bandwidth, more objects and larger objects could be forwarded to the client. However, in contrast, if the bandwidth of the link is lower, then prefetch response abort 142 (FIG. 1) may be more selective when deciding whether to forward the prefetched object. In one embodiment, the bandwidth of the link is assigned a point value which may be factored into the determination of whether to forward the object.

At process block 225, the latency of the link between proxy server 132 (FIG. 1) and proxy client 112 (FIG. 1) is determined. In one embodiment, the latency of the link is based on the current round trip time (RTT) of the link. Accordingly, if the RTT is high, then it may be more beneficial to forward the prefetched object to the client because of the round trip savings gained by forwarding the object. However, if the RTT is low, then the saved round trip may be of less value for optimization purposes. In one embodiment, the latency of the link is assigned a point value which may be factored into the determination of whether to forward the object.

In process block 230, the initial prefetch time is determined (i.e., how long the object took to be retrieved from the Internet). If the object took a long time to retrieve from the Internet, then it may be optimal to forward the object to the client in order to avoid re-downloading the object in the future. Furthermore, if the object was downloaded quickly, then less optimization may be gained from forwarding the object to the client. Hence, in one embodiment, the download time of the object may be assigned a point value which may be factored into determining whether to forward the object to the client. In an alternative embodiment, the aborted objects may be stored on proxy server 132 (FIG. 1) in case they are subsequently requested. Accordingly, if these objects are stored and then requested, the download will not need to be repeated. If this approach is implemented, then process block 230 may not be used.

At process block 235, a cost/benefit analysis may be preformed to determine whether to forward the prefetched object. In one embodiment, the above-mentioned point values may be calculated to determine if the object meets a predetermined threshold. In an alternative embodiment, the cost of forwarding the object may be determined using the following equation:

Cost=ObjectSize*(1.0−ProbabilityofUse)/Bandwidth

Furthermore, in one embodiment, the benefit of forwarding the prefetched object may be determined using the following equation:

Benefit=ProbabilityofUse*(RTT+PrefetchTime)

Accordingly, by using these or other equations, at decision block 240, if the cost value is greater than the benefit value, then the prefetched object is aborted and the object is not forwarded to the client (process block 245). Conversely, if the benefit is greater than the cost, then the prefetched object is forwarded to the client (process block 250). In an alternative embodiment, objects that have been aborted may be cached at, for example, proxy server 132 (FIG. 1), in the event that the client subsequently requests the object. Hence, the above referenced equation may be reduced to:

Benefit=ProbabilityofUse*RTT

The equation is reduced in this manner because, since the object has already been downloaded, it would not need to be re-downloaded from the originating server.

A number of variations and modifications of the disclosed embodiments can also be used. For example, the factors used to determine whether to forward a prefetched object may be used outside the website and/or Internet context. For example, the prefetching technique may be used to determine which terminals to download an object from in a peer-to-peer network environment. In addition, the prefetching technique may be used on various network types, for example, a satellite network, a mobile device network, etc.

Referring now to FIG. 3, a system 300 for providing network acceleration is illustrated. In one embodiment, user system 102 in FIG. 1 may be client 305 and proxy client 112 in FIG. 1 may be proxy client 310. Client 305 may generate a request for content from content server 330. In one embodiment, content server 330 may be a web server, a file server, a mail server, etc., and the content request may be for a file, a webpage, an email message, etc.

Proxy client 310 may be configured to intercept the content request from client 305 and transmit the request over high latency link 315 to proxy server 320 on behalf of client 305. In one embodiment, high latency link 315 may be a satellite link, a cellular link, a wireless link, etc. In one embodiment, the content request may include references to prefetchable content. Accordingly, proxy server 320, while prefetching objects for network acceleration, would utilize the prefetch abort systems and methods described in FIGS. 1 and 2.

In a further embodiment, communications between proxy server 320 and content server 330 over low latency link 325 are sufficiently fast that acceleration is not needed or would not provide sufficient benefit for the cost needed to accelerate. Hence, upon receipt of communications from content server 330, proxy server 320 accelerates the communications between proxy server 320 and proxy client 310 in order to accelerate communications over high latency link 315. Accordingly, the network traffic over high latency link 315 is accelerated while network traffic over low latency link 325 remains relatively unchanged.

FIG. 4 provides a schematic illustration of one embodiment of a computer system 400 that can perform the methods of the invention, as described herein, and/or can function, for example, as any part of client 305, proxy server 320, or content server 330 in FIG. 3. It should be noted that FIG. 4 is meant only to provide a generalized illustration of various components, any or all of which may be utilized, as appropriate. FIG. 4, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner.

The computer system 400 is shown comprising hardware elements that can be electrically coupled via a bus 405 (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors 410, including, without limitation, one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration chips, and/or the like); one or more input devices 415, which can include, without limitation, a mouse, a keyboard, and/or the like; and one or more output devices 420, which can include, without limitation, a display device, a printer, and/or the like.

The computer system 400 may further include (and/or be in communication with) one or more storage devices 425, which can comprise, without limitation, local and/or network accessible storage and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like. The computer system 400 might also include a communications subsystem 430, which can include, without limitation, a modem, a network card (wireless or wired), an infra-red communication device, a wireless communication device, and/or chipset (such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc.), and/or the like. The communications subsystem 430 may permit data to be exchanged with a network (such as the network described below, to name one example), and/or any other devices described herein. In many embodiments, the computer system 400 will further comprise a working memory 435, which can include a RAM or ROM device, as described above.

The computer system 400 also can comprise software elements, shown as being currently located within the working memory 435, including an operating system 440 and/or other code, such as one or more application programs 445, which may comprise computer programs of the invention, and/or may be designed to implement methods of the invention and/or configure systems of the invention, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer). A set of these instructions and/or code might be stored on a computer readable storage medium, such as the storage device(s) 425 described above. In some cases, the storage medium might be incorporated within a computer system, such as the system 400. In other embodiments, the storage medium might be separate from a computer system (i.e., a removable medium, such as a compact disc, etc.), and/or provided in an installation package, such that the storage medium can be used to program a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system 400 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 400 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.

It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.

In one aspect, the invention employs a computer system (such as the computer system 400) to perform methods of the invention. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 400 in response to processor 410 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 440 and/or other code, such as an application program 445) contained in the working memory 435. Such instructions may be read into the working memory 435 from another machine-readable medium, such as one or more of the storage device(s) 425. Merely by way of example, execution of the sequences of instructions contained in the working memory 435 might cause the processor(s) 410 to perform one or more procedures of the methods described herein.

The terms “machine-readable medium” and “computer readable medium”, as used herein, refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer system 400, various machine-readable media might be involved in providing instructions/code to processor(s) 410 for execution and/or might be used to store and/or carry such instructions/code (e.g., as signals). In many implementations, a computer readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as the storage device(s) 425. Volatile media includes, without limitation, dynamic memory, such as the working memory 435. Transmission media includes coaxial cables, copper wire, and fiber optics, including the wires that comprise the bus 405, as well as the various components of the communications subsystem 430 (and/or the media by which the communications subsystem 430 provides communication with other devices). Hence, transmission media can also take the form of waves (including, without limitation, radio, acoustic, and/or light waves, such as those generated during radio-wave and infra-red data communications).

Common forms of physical and/or tangible computer readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.

Various forms of machine-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 410 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system 400. These signals, which might be in the form of electromagnetic signals, acoustic signals, optical signals, and/or the like, are all examples of carrier waves on which instructions can be encoded, in accordance with various embodiments of the invention.

The communications subsystem 430 (and/or components thereof) generally will receive the signals, and the bus 405 then might carry the signals (and/or the data, instructions, etc., carried by the signals) to the working memory 435, from which the processor(s) 405 retrieves and executes the instructions. The instructions received by the working memory 435 may optionally be stored on a storage device 425 either before or after execution by the processor(s) 410.

A set of embodiments comprises systems for implementing staged configurator modeling. In one embodiment, proxy server 320 and/or client 305 (as shown in FIG. 3) may be implemented as computer system 400 in FIG. 4. Merely by way of example, FIG. 5 illustrates a schematic diagram of a system 500 that can be used in accordance with one set of embodiments. The system 500 can include one or more user computers 505. The user computers 505 can be general purpose personal computers (including, merely by way of example, personal computers and/or laptop computers running any appropriate flavor of Microsoft Corp.'s Windows™ and/or Apple Corp.'s Macintosh™ operating systems) and/or workstation computers running any of a variety of commercially-available UNIX™ or UNIX-like operating systems. These user computers 505 can also have any of a variety of applications, including one or more applications configured to perform methods of the invention, as well as one or more office applications, database client and/or server applications, and web browser applications. Alternatively, the user computers 505 can be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, and/or personal digital assistant (PDA), capable of communicating via a network (e.g., the network 510 described below) and/or displaying and navigating web pages or other types of electronic documents. Although the exemplary system 500 is shown with three user computers 505, any number of user computers can be supported.

Certain embodiments of the invention operate in a networked environment, which can include a network 510. The network 510 can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including, without limitation, TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 510 can be a local area network (“LAN”), including, without limitation, an Ethernet network, a Token-Ring network and/or the like; a wide-area network (WAN); a virtual network, including, without limitation, a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network, including, without limitation, a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in the art, and/or any other wireless protocol; and/or any combination of these and/or other networks.

Embodiments of the invention can include one or more server computers 515. Each of the server computers 515 may be configured with an operating system, including, without limitation, any of those discussed above, as well as any commercially (or freely) available server operating systems. Each of the servers 515 may also be running one or more applications, which can be configured to provide services to one or more user computers 505 and/or other servers 515.

Merely by way of example, one of the servers 515 may be a web server, which can be used, merely by way of example, to process requests for web pages or other electronic documents from user computers 505. The web server can also run a variety of server applications, including HTTP servers, FTP servers, CGI servers, database servers, Java™ servers, and the like. In some embodiments of the invention, the web server may be configured to serve web pages that can be operated within a web browser on one or more of the user computers 505 to perform methods of the invention.

The server computers 515, in some embodiments, might include one or more application servers, which can include one or more applications accessible by a client running on one or more of the client computers 505 and/or other servers 515. Merely by way of example, the server(s) 515 can be one or more general purpose computers capable of executing programs or scripts in response to the user computers 505 and/or other servers 515, including, without limitation, web applications (which might, in some cases, be configured to perform methods of the invention). Merely by way of example, a web application can be implemented as one or more scripts or programs written in any suitable programming language, such as Java™, C, C#™ or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The application server(s) can also include database servers, including without limitation those commercially available from Oracle™, Microsoft™, Sybase™, IBM™, and the like, which can process requests from clients (including, depending on the configurator, database clients, API clients, web browsers, etc.) running on a user computer 505 and/or another server 515. In some embodiments, an application server can create web pages dynamically for displaying the information in accordance with embodiments of the invention, such as information displayed on web browser 106 in FIG. 1. Data provided by an application server may be formatted as web pages (comprising HTML, Javascript, etc., for example) and/or may be forwarded to a user computer 505 via a web server (as described above, for example). Similarly, a web server might receive web page requests and/or input data from a user computer 505 and/or forward the web page requests and/or input data to an application server. In some cases a web server may be integrated with an application server.

In accordance with further embodiments, one or more servers 515 can function as a file server and/or can include one or more of the files (e.g., application code, data files, etc.) necessary to implement methods of the invention incorporated by an application running on a user computer 505 and/or another server 515. Alternatively, as those skilled in the art will appreciate, a file server can include all necessary files, allowing such an application to be invoked remotely by a user computer 505 and/or server 515. It should be noted that the functions described with respect to various servers herein (e.g., application server, database server, web server, file server, etc.) can be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters.

In certain embodiments, the system can include one or more databases 520. The location of the database(s) 520 is discretionary: merely by way of example, a database 520 a might reside on a storage medium local to (and/or resident in) a server 515 a (and/or a user computer 505). Alternatively, a database 520 b can be remote from any or all of the computers 505 or servers 515, so long as the database 520 b can be in communication (e.g., via the network 510) with one or more of these. In a particular set of embodiments, a database 520 can reside in a storage-area network (“SAN”) familiar to those skilled in the art. (Likewise, any necessary files for performing the functions attributed to the computers 505 or servers 515 can be stored locally on the respective computer and/or remotely, as appropriate.) In one set of embodiments, the database 520 can be a relational database, such as an Oracle™ database, that is adapted to store, update, and retrieve data in response to SQL-formatted commands. The database might be controlled and/or maintained by a database server, as described above, for example.

Accumulator Embodiments

As will be appreciated from the above description, prefetching systems may seek to request objects that will subsequently be requested when a web page is rendered. Notably, much of the information about those objects may be unknown. For example, the exact set of objects to be ultimately requested by a client may not be known for certain in advance. Further, a server-side prefetcher may not have full knowledge of a client-side browser configuration or the contents of a client-side browser cache. Even further, the prefetcher may not be able to fully parse scripts in which object references are found, thereby further limiting certainty as to whether an object will be requested. As such, effectiveness and efficiency of a prefetching system may hinge on establishing appropriate cost-benefit analysis techniques.

As discussed above, the prefetching cost-benefit may be analyzed as a function of a number of factors, including probability of use, round-trip time (RTT), prefetch time, available bandwidth, object size, etc. Illustrative equations to this effect are described above with reference to FIG. 2. These various factors may be weighed to determine whether prefetching one or more objects is efficient, for example, as compared to downloading the object only when it is actually requested by the client.

Typically, satisfying requests for objects over a communications system (e.g., a satellite communications system) involves multiple sources of delay. In one embodiment, a user requests an object from a content server (e.g., via a web browser on a user system). The request is processed by an intermediate proxy client and proxy server (e.g., as shown in FIG. 3). The proxy server requests the object from the content server, receives the object from the content server in response to the request, and forwards the object to the user system via the proxy client. From the perspective of the proxy server, delays are introduced through communications with the content server (e.g., from delays in getting a response from the content server) and from communications with the client (e.g., from latency in the communication link between the proxy server and the proxy client). For example, in many high-latency communication systems (e.g., a satellite communications system), delays resulting from communications with the client may largely be due to the round-trip time over the communication link.

Embodiments of prefetching systems may be used to address one or both of these types of delay. In one example, a requested object is not prefetched. A first delay may be introduced while the proxy server waits to receive the requested object, and a second delay may be introduced according to the RTT between the server and client sides of the system. In another example, an object is prefetched. As there may be no need to send a request to the content server, the associated delay (the first delay in the preceding example) may be substantially eliminated. Further, while the RTT of the system may be unaffected by the prefetching (e.g., it is a physical property of the system), link usage in response to the request may be substantially minimized. For instance, rather than sending a large object over the link in response to the request, only a small message may be sent indicating to the client that a cached version of the object should be used.

It is worth noting that some system benefits of prefetching may tend to be relatively unrelated to the size of the object being prefetched, as the benefits may be most apparent when the object is ultimately requested. For example, even though a user may experience an apparent increase in speed by having the object sent to the user prior to a request, the amount of bandwidth used by the system is substantially the same regardless of when the object is sent over the link (e.g., whether it is sent as a prefetched object or sent in response to an actual request). On the contrary, however, some system costs associated with prefetching may be highly dependent on object size, as the costs may be most apparent when the object is not ultimately prefetched. For example, if a large object is prefetched and is not ultimately requested by the user, the link may be unnecessarily congested. This may delay the downloading of objects that are actually requested.

Thus, once values of certain variables have been established (e.g., once link conditions and other environmental variables are established and the probability of use is estimated using various techniques), the decision whether it is efficient to prefetch an object may essentially become a function of object size. In some embodiments, the prefetching system determines that it is efficient to prefetch the object if the object size is less than some threshold value; while the prefetching system determines that it is inefficient to prefetch the object if the object size is larger than the threshold value.

At times, however, determining the object size prior to prefetching the object may be difficult or impossible. In some embodiments of prefetch abort systems, objects may be downloaded speculatively to the optimizing proxy server to determine the size. If the object size is less than the threshold for efficient prefetching, then the object may be prefetched. If it is larger, the object is not prefetched. This approach, however, may be limited in a number of ways. One limitation is that the size of an object may not be specified in the header. If the prefetcher aborts the transfer and the file was small, the benefits of prefetching are lost. If the prefetcher starts to download the file and the file is large, then unnecessary link congestion occurs. Another limitation is that, if the prefetcher decides to abort an object because it is too large and the browser subsequently requests the object, then the object must be requested again from the content server.

Embodiments of prefetch abort systems include an accumulator configured to address one or more of these limitations. During a prefetch operation, the accumulator accumulates file data until sufficient data is available to make an effective abort decision. In some embodiments, the accumulator is implemented by the prefetch response abort 142 block of FIG. 1. For example, the prefetch response abort 142 of FIG. 1 may use the accumulator to help determine the object size in block 210 of the method 200 of FIG. 2.

FIG. 6 shows a flow diagram of an illustrative method 600 for prefetching using an accumulator, according to various embodiments. FIG. 7 shows relevant portions of an illustrative communications system 700, including an accumulator for a prefetch abort system, according to various embodiments. The system 700 includes a proxy server 132 in communication with a user system 102 (e.g., via a proxy client, over a high-latency link 130) and a content server 330 (e.g., over a relatively low latency link 156). The proxy server 132 may be the proxy server 132 of FIG. 1, including prefetch response abort 142. As discussed below, prefetch response abort 142 is in communication with prefetch object compressor 702 and prefetch accumulator 704. The prefetch accumulator 704 may be further in communication with an accumulator buffer 710 and/or an output data store 720. For the sake of clarity, the components of the system 700 of FIG. 7 will be discussed in parallel with associated portions of the method 600 of FIG. 6.

The method 600 begins at block 604 by determining an appropriate size threshold for efficient prefetching of an object. In some embodiments, the size threshold is determined by prefetch response abort 142, as discussed with reference to FIG. 2 above. If transfer time is a primary concern, the size threshold may be determined as a function of the cost benefit equations described above, as follows. The cost of prefetching may be calculated in some embodiments according to the equation:

Cost=ObjectSize*(1.0−ProbabilityofUse)/Bandwidth

For example, “ObjectSize” is the size of the object being evaluated for prefetching, “ProbabilityofUse” is the probability the object will be ultimately requested by the user system 102 (e.g., requested by the client browser), and “Bandwidth” is the bandwidth usage on the high-latency link 130 from pushing the object to the user system 102. The benefit of prefetching may be calculated in some embodiments according to the equation:

Benefit=ProbabilityofUse*(RTT+PrefetchTime)

For example, “RTT” is the round-trip time for communications over the high-latency link 130 and “PrefetchTime” is the time it takes to download (e.g., and possibly to compress) the object from the content server 330. The maximum efficient object size may be considered in some embodiments as the object size where the cost of prefetching is equal to the benefit of prefetching (i.e., if the object size increases further, the cost will increase without increasing the benefit, causing the cost to exceed the benefit). Setting the cost and benefit equations equal to each other and solving for the object size may yield the following equation for the maximum efficient object size for prefetching:

MaximumSize=ProbabilityofUse*(RTT+PrefetchTime)*Bandwidth/(1.0−ProbabilityofUse)

It is worth noting that, while this equation may maximize performance experienced by one user, this threshold object size may be adjusted in response to other issues or for other reasons. For example, if a link is congested, the maximum size may be reduced to reflect the impact of the bandwidth consumption on other users. It is further worth noting that other types of metrics or thresholds may be used.

At block 608, downloading of the prefetched object may begin. For example, the object is retrieved from the content server 330 by the proxy server 132, but may not be sent over the high-latency link 130 to the user system 102. At block 612, the downloaded data is accumulated in the prefetch accumulator 704 (e.g., in an accumulator buffer 710). At block 620, the size of the accumulated data may be evaluated to determine whether the maximum size threshold has been reached.

In some embodiments, at block 616, the data may be compressed by the prefetch object compressor 702 prior to being sent (or as it is sent) to the prefetch accumulator 704. Notably, compressing the data with the prefetch object compressor 702 prior to accumulation in the accumulator buffer 710 may allow the calculations to more accurately reflect the ultimate cost to the high-latency link 130 of sending the object to the user system 102. For example, if a file is highly compressible, the bandwidth cost to the high-latency link 130 may be reduced. As such, it may still be efficient to push the object to the user system 102 in its compressed form, even if its uncompressed object size would exceed the size threshold. In some embodiments, the size of the accumulated data is evaluated according to the compressed size in block 620 when determining whether the maximum size threshold has been reached.

A determination is then made at block 624 as to whether it is efficient to push the object to the user system 102 over the high-latency link 130. In some embodiments, this determination is made as a function of the determination in block 620. For example, the equation for determining the size threshold may include all the relevant factors for making the ultimate cost benefit determination. If the end of the object file is reached before reaching the size threshold, it may be determined that pushing the object to the user system 102 is efficient; if the object size threshold is reached before the end of file, then it may not be efficient to push the object to the user system 102. In this way, embodiments may make the correct decision whether to prefetch the file data even where the file size is not specified in the header. In other embodiments, the determination at block 624 may account for additional factors not evaluated as part of the size threshold equations. For example, the determination of whether it is efficient to push the object to the user system 102 may be affected by communications with other users (e.g., multicasting opportunities, link congestion, etc.) or other factors.

If the decision is made to push the prefetched data to the user system 102 at block 624, the object (e.g., compressed or uncompressed) may be pushed to the user system 102 at block 628. If the decision is made not to push the prefetched data to the user system 102 at block 624, the prefetch operation may be aborted at block 632. In some embodiments, the accumulated data (e.g., the compressed data in the accumulator buffer 710) can be pushed to an output data store 720 (e.g., an output buffer) at block 640. As part of storing the data at the output data store 720 in block 640, various additional functions may be performed. For example, the data may be parsed, indexed, logged, further compressed, etc.

In certain embodiments, when the decision is made not to push the prefetched data to the client at block 624, a further determination is made as to whether the data should be accumulated past the threshold size value (e.g., in the accumulator buffer 710 or the output data store 720) at block 636. For example, it may be more efficient to compress a larger amount of data prior to storage in block 640. Notably, continued accumulation may typically increase performance for the user, as the prefetch time is saved without sacrificing bandwidth on the high-latency link 130. However, continued downloading, compression, and storage may use excessive amounts of resources on the proxy server 132. In one embodiment, the accumulation continues only until a second threshold is reached, after which the proxy server 132 closes the connection to the content server 330. If the client (e.g., browser) subsequently requests the object, the accumulated data can be sent (e.g., from the output data store 720) while the remainder of the file is downloaded and compressed by the prefetcher (e.g., and/or accumulated by the prefetch accumulator 704). The second threshold may be set so that the time needed to transfer the accumulated data may be long enough to compensate for the delay in reestablishing a connection over the low latency link 156 to the content server 330. In this way, savings in the prefetch time may be achieved without excessive consumption of memory and processing resources on the proxy server 132.

It is worth noting that, if the client browser subsequently requests a stored object, the data may effectively be immediately available; no further delays may be created by fetching another copy from the content server 330 or by compressing a new data object. As such, savings in prefetch time may be achieved even though the data was not pushed across the high-latency link 130.

It is further worth noting that the accumulated data (e.g., stored in the accumulator buffer 710 and/or the output data store 720 can be further exploited to provide additional functionality. FIG. 8 shows an illustrative method 800 for exploiting accumulated data to further optimize prefetch abort operations, according to various embodiments. In some embodiments, the method 800 is performed by the system 700 of FIG. 7.

The method 800 begins at block 805 by receiving a prefetched object from a content server 330. It will be appreciated from the discussion of FIGS. 6 and 7 that, even though the object has already been prefetched, it may still be inefficient to forward the object to the user system 102. For example, bandwidth and/or other constraints may affect a determination of whether it is efficient to communicate objects over the high-latency link 130 between the proxy server 132 and the user system 102.

As such, accumulated prefetched objects may be analyzed (e.g., in addition to other factors, such as link conditions) to gather and/or generate various additional cost-benefit data for optimizing the prefetch operation. In some embodiments, the byte sequence of the prefetched object is analyzed at block 810. A determination may then be made in block 815 of whether the bytes are the same as an object that was previously prefetched from a different URL. For example, data in the accumulator buffer 710 may be processed using delta coding and/or other techniques to generate a fingerprint of the accumulated data. The fingerprint may be compared against fingerprints of previously accumulated data (e.g., data stored in the output data store 720).

In other embodiments, the object size is determined at block 820. As discussed above, the object size may be significant in determining whether it is efficient to forward the object to the client. In some embodiments, if the object is large (e.g., or in all cases), a determination is made as to whether the object content is compressible, scalable, etc. at block 825. For example, the determination may be made by the prefetch object compressor 702. In certain embodiments, this determination is made as a function of analyzing the byte sequence in block 810. If the content is compressible, scalable, etc., embodiments of the method 800 revise the effective object size at block 830. For example, the method 800 may estimate the compressed size of the object and use that compressed size as the effective size of the object when making prefetching determinations.

In still other embodiments, other cost-benefit data is gathered and/or generated. In one embodiment, at block 840, the communication link between the proxy client and the proxy server (e.g., or between the proxy server and the network) may be evaluated to determine various link conditions. This type of information may be received from external sources, estimated, measured, etc. For example, the links may be analyzed to determine bandwidth, traffic, latency, packet errors, etc. Similarly, latency of the high-latency link 130 may be estimated in block 840 based on a current round-trip time (“RTT”) measure. Accordingly, if the RTT is high, then it may be more beneficial to forward the prefetched object to the client because of the round trip savings gained by forwarding the object. However, if the RTT is low, then the saved round trip may be of less value for optimization purposes.

In another embodiment, the method 800 determines the probability that an object will be used at block 850. In some embodiments described above (e.g., those without accumulator functionality), URL parsing and/or other techniques can be used to help make that determination. For example, certain popular website content may be more likely requested and/or accessed by users of a communication network. In embodiments of prefetching that include accumulator functionality, the determination at block 850 may be made as a function of analyzing the byte sequence in block 810. For example, fingerprinting may be used, as described above, to determine if the object has been requested before by that user or by some threshold number of other users.

The various types of data collected and/or generated in the various blocks (e.g., blocks 830, 815, 840, and 850) may be used to estimate prefetch time in block 860. For example, current link conditions and object size may drive an estimation of the time it will take to prefetch a particular object. Other data may also be used. For example, if the object was previously prefetched (e.g., or a similar object), that data can be used to make predictions. Particularly, if the object took a long time to retrieve from the Internet a previous time, then it may be optimal to forward the object to the client in order to avoid re-downloading the object in the future. Furthermore, if the object was downloaded quickly, then less optimization may be gained from forwarding the object to the client. Hence, in one embodiment, the download time of the object may be assigned a point value which may be factored into determining whether to forward the object to the client.

In some embodiments, some or all of these data can be used to perform a cost-benefit analysis on the prefetched object at block 865. The result of the cost-benefit analysis performed at block 865 can be evaluated at decision block 870 to determine whether the benefits of prefetching the object outweigh the costs of prefetching the object. If the benefits outweigh the costs, the object is prefetched at block 880. If the benefits fail to outweigh the costs, the object is not prefetched, or the prefetch operation is aborted at block 875.

A number of variations and modifications of the disclosed embodiments can also be used. For example, factors used to determine whether to forward a prefetched object may be used outside the website and/or Internet context. For example, the prefetching technique may be used to determine which terminals to download an object from in a peer-to-peer network environment. In addition, the prefetching technique may be used on various network types, for example, a satellite network, a mobile device network, etc.

While the invention has been described with respect to exemplary embodiments, one skilled in the art will recognize that numerous modifications are possible. For example, the methods and processes described herein may be implemented using hardware components, software components, and/or any combination thereof. Further, while various methods and processes described herein may be described with respect to particular structural and/or functional components for ease of description, methods of the invention are not limited to any particular structural and/or functional architecture but instead can be implemented on any suitable hardware, firmware, and/or software configurator. Similarly, while various functionalities are ascribed to certain system components, unless the context dictates otherwise, this functionality can be distributed among various other system components in accordance with different embodiments of the invention.

Moreover, while the procedures comprised in the methods and processes described herein are described in a particular order for ease of description, unless the context dictates otherwise, various procedures may be reordered, added, and/or omitted in accordance with various embodiments of the invention. Moreover, the procedures described with respect to one method or process may be incorporated within other described methods or processes; likewise, system components described according to a particular structural architecture and/or with respect to one system may be organized in alternative structural architectures and/or incorporated within other described systems. Hence, while various embodiments are described with—or without—certain features for ease of description and to illustrate exemplary features, the various components and/or features described herein with respect to a particular embodiment can be substituted, added, and/or subtracted from among other described embodiments, unless the context dictates otherwise. Consequently, although the invention has been described with respect to exemplary embodiments, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims. 

1. A method for handling object data as part of a prefetch operation in a communications system, the method comprising: commencing downloading of object data of a prefetch object from a content server using a prefetch server communicatively coupled with the content server; accumulating the object data in an accumulator at the prefetch server; checking an accumulated size of the accumulated object data; determining, at the prefetch server and as a function of the accumulated size of the accumulated object data, whether the cost of pushing the object data to a client over a communication link of the communications system exceeds the benefit of pushing the object data to the client over the communication link of the communications system; and when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, aborting the prefetch operation.
 2. The method of claim 1, further comprising: when the cost of pushing the object data to the client does not exceed the benefit of pushing the object data to the client, pushing the object data to the client.
 3. The method of claim 1, further comprising: when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, pushing the object data to an output data store.
 4. The method of claim 3, further comprising: receiving a request for the prefetch object from the client at the prefetch server subsequent to pushing the object data to the output data store; and satisfying the request by pushing the object data from the output data store to the client.
 5. The method of claim 1, further comprising: compressing the object data into compressed object data at the accumulator.
 6. The method of claim 5, wherein checking the accumulated size of the accumulated object data comprises checking the accumulated size of the compressed object data.
 7. The method of claim 5, further comprising: when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, pushing the compressed object data to an output data store.
 8. The method of claim 5, further comprising: when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client: accumulating additional object data in the accumulator at the prefetch server, wherein compressing the object data comprises compressing the additional object data into the compressed object data at the accumulator; and pushing the compressed object data to an output data store.
 9. The method of claim 1, further comprising: determining, at the prefetch server, a threshold value indicating a threshold size of the prefetch object, such that the cost of pushing the object data to the client is substantially equal to the benefit of pushing the object data to the client when the accumulated size of the accumulated data is substantially equal to the threshold size.
 10. The method of claim 9, wherein determining whether the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client comprises: determining whether the accumulated size of the accumulated object data exceeds the threshold value.
 11. The method of claim 9, wherein the threshold value is determined as a function of at least one of: a probability of use of the prefetch object by the client; a communication time relating to communication of the prefetch object between the content server and the prefetch server; or a communication time relating to communication of the prefetch object between the prefetch server and the client.
 12. The method of claim 9, wherein the threshold value is determined such that: S=[P*(T _(RT) +T _(PF))*B]/(1−P), wherein S indicates the threshold value, P indicates a probability of use of the prefetch object by the client, B indicates a bandwidth of the communication link of the communications system between the prefetch server and the client, T_(RT) indicates a round-trip time for communicating the prefetch between the prefetch server and the client, and T_(PF) indicates a prefetch time for downloading the prefetch object from the content server to the prefetch server.
 13. The method of claim 1, wherein: the proxy server is in communication with the content server over a first communication link; the proxy server is in communication with the client over a second communication link; and latency of the first communication link is substantially low relative to latency of the second communication link.
 14. A system for handling object data as part of a prefetch operation in a communications system, the system comprising: a proxy server located at a server-side node of the communications system, the proxy server being communicatively coupled with a content server and with a client located at a client-side node of the communications system, the proxy server comprising: an accumulator configured to accumulate object data of a prefetch object; and a prefetch server, communicatively coupled with the accumulator and configured to: download the object data from the content server to the accumulator; check an accumulated size of the accumulated object data; determine, as a function of the accumulated size of the accumulated object data, whether the cost of pushing the object data to the client over a communication link of the communications system exceeds the benefit of pushing the object data to the client over the communication link of the communications system; and when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, aborting the prefetch operation.
 15. The system of claim 14, the prefetch server being further configured to: push the object data to the client when the cost of pushing the object data to the client does not exceed the benefit of pushing the object data to the client.
 16. The system of claim 14, further comprising: an output data store, communicatively coupled with the proxy server, wherein the prefetch server is further configured to push the object data to the output data store when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client.
 17. The system of claim 16, the prefetch server being further configured to: receive a request for the prefetch object from the client subsequent to pushing the object data to the output data store; retrieve the object data from the output data store; and push the object data from the output data store to the client in response to the request.
 18. The system of claim 14, further comprising: a prefetch compressor, communicatively coupled with the accumulator and configured to compress the object data into compressed object data at the accumulator.
 19. The system of claim 14, the prefetch server being further configured to: determine a threshold value indicating a threshold size of the prefetch object, such that the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client when the accumulated size of the accumulated data exceeds the threshold size.
 20. A machine-readable medium for handling object data as part of a prefetch operation in a communications system, the machine-readable medium having instructions stored thereon which, when executed by a machine, cause the machine to perform steps comprising: commencing downloading of object data of the prefetch object from a content server communicatively coupled with the machine; accumulating the object data in an accumulator; checking an accumulated size of the accumulated object data; determining, as a function of the accumulated size of the accumulated object data, whether the cost of pushing the object data to a client communicatively coupled with the machine over a communication link of the communications system exceeds the benefit of pushing the object data to the client over the communication link of the communications system; and when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, aborting the prefetch operation.
 21. The machine-readable medium of claim 20, the instructions stored thereon, when executed by the machine, causing the machine to perform steps further comprising: when the cost of pushing the object data to the client does not exceed the benefit of pushing the object data to the client, pushing the object data to the client.
 22. The machine-readable medium of claim 20, the instructions stored thereon, when executed by the machine, causing the machine to perform steps further comprising: when the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client, pushing the object data to an output data store communicatively coupled with the machine.
 23. The machine-readable medium of claim 20, the instructions stored thereon, when executed by the machine, causing the machine to perform steps further comprising: compressing the object data into compressed object data at the accumulator.
 24. The machine-readable medium of claim 20, the instructions stored thereon, when executed by the machine, causing the machine to perform steps further comprising: determining a threshold value indicating a threshold size of the prefetch object, such that the cost of pushing the object data to the client exceeds the benefit of pushing the object data to the client when the accumulated size of the accumulated data exceeds the threshold size. 